How I can found out by DXL script who and when a view is created.
esohgol - Tue Feb 16 07:17:39 EST 2010 |
|
Re: Doors views
doors36677 - Tue Feb 16 10:20:44 EST 2010
Assuming I understood your question correctly -- this info is not available thru dxl.
|
|
Re: Doors views
esohgol - Tue Feb 16 10:55:18 EST 2010 doors36677 - Tue Feb 16 10:20:44 EST 2010
Assuming I understood your question correctly -- this info is not available thru dxl.
My question is by writing a DXL script find out who create a specific view in a current module and when.
BR Sohail
|
|
Re: Doors views
llandale - Tue Feb 16 16:12:31 EST 2010
There is no History for views so you cannot figure that out via the GUI no by DXL.
If you have access to the database files, however, I suppose you could figure it out by finding the folder housing your module, going to views, finding the files that house your view, and checking the date. That won't tell you 'who'.
|
|
Re: Doors views
kbmurphy - Tue Feb 16 16:39:10 EST 2010 esohgol - Tue Feb 16 10:55:18 EST 2010
Hi,
My question is by writing a DXL script find out who create a specific view in a current module and when.
BR Sohail
|
|
Re: Doors views
ZenMonkey760 - Tue Feb 23 16:32:45 EST 2010
This won't be of any use for views already in existence, but one solution you could employ going forward...
Have a module level text attribute for each module to store a listing of views for your module and their creation date.
e.g. module."Public Views"
Standard View, 2010-02-01
Public View 1, 2010-02-02
Public View 2, 2010-02-06
Alternatively, have one module level attribute (using Date type) for each view.
e.g. module."View-Standard View" = 2010-02-01
module."View-Public View 1" = 2010-02-02
module."View-Public View 2" = 2010-02-06
Have a trigger that activates upon close of modules that looks at all the available views in the module (see "for view in module" in the DXL manual) and compares the available views to the listing in the "Public Views" module attribute[s]. (you'll need to parse each line of the first example given above to extract the view names, or append the name of each view to the string "View-" in the second example.)
If a view has been created that doesn't exist in the listing, you'll need to ensure that the module is open for editing. Then, either append the new view name and the current date to the first example or create a new attribute and assign the current date to the value as in the second example.
The first example has the benefit of being able to easily rebuild the listing of views each time the module is closed to remove views that have been deleted or renamed. The second example could also work, but would require a bit more effort.
I hope this helps.
|
|
Re: Doors views
esohgol - Wed Feb 24 02:33:12 EST 2010 ZenMonkey760 - Tue Feb 23 16:32:45 EST 2010
This won't be of any use for views already in existence, but one solution you could employ going forward...
Have a module level text attribute for each module to store a listing of views for your module and their creation date.
e.g. module."Public Views"
Standard View, 2010-02-01
Public View 1, 2010-02-02
Public View 2, 2010-02-06
Alternatively, have one module level attribute (using Date type) for each view.
e.g. module."View-Standard View" = 2010-02-01
module."View-Public View 1" = 2010-02-02
module."View-Public View 2" = 2010-02-06
Have a trigger that activates upon close of modules that looks at all the available views in the module (see "for view in module" in the DXL manual) and compares the available views to the listing in the "Public Views" module attribute[s]. (you'll need to parse each line of the first example given above to extract the view names, or append the name of each view to the string "View-" in the second example.)
If a view has been created that doesn't exist in the listing, you'll need to ensure that the module is open for editing. Then, either append the new view name and the current date to the first example or create a new attribute and assign the current date to the value as in the second example.
The first example has the benefit of being able to easily rebuild the listing of views each time the module is closed to remove views that have been deleted or renamed. The second example could also work, but would require a bit more effort.
I hope this helps.
Regards
Sohail
|
|